Course Registration System
Use-Case Specification
Register for Courses Use Case
Version: Draft
Revision History
Date |
Version |
Description |
Author |
21/Dec/98 |
Draft |
Draft Version |
S. Gamble |
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
- Brief Description
- Flow of Events
- Basic Flow – Create a
Schedule
- Alternative Flows
- Modify a Schedule
- Delete a Schedule
- Course Catalog System
Unavailable
- Special Requirements
- Pre-Conditions
- Login
- Post-Conditions
- Extension Points
Register
for Courses Use Case
- Brief Description
This use case allows a Student to register for course offerings in the
current semester. The Student can also modify or delete course selections if
changes are made within the add/drop period at the beginning of the semester.
The Course Catalog System provides a list of all the course offerings for the
current semester.
The main actor of this use case is the Student. The Course Catalog System is
an actor within the use case.
Flow
of Events
The use case begins when the Student selects the "maintain
schedule" activity from the Main Form.
Basic
Flow – Create a Schedule
- The Student selects "create schedule."
- The system displays a blank schedule form.
- The system retrieves a list of available course
offerings from the Course Catalog System.
- The Student selects 4 primary course offerings and 2
alternate course offerings from the list of available offerings. Once
the selections are complete the Student selects "submit."
- Courses are added for each selected course offering.
- The system saves the schedule.
Alternative
Flows
- Modify a Schedule
TBD.
Delete a Schedule
TBD.
Course Catalog
System Unavailable
If, the system is unable to communicate with the Course Catalog System
after a specified number of tries, the system will display an error
message to the Student. The Student acknowledges the error message and the
use case terminates.
Special
Requirements
Special requirements will be determined during the next iteration.
Pre-Conditions
Login
Before this use case begins the Student has logged onto the system.
Post-Conditions
Post-conditions will be determined during the next iteration.
Extension Points
- Extension points of the business use case will be identified during the
Elaboration Phase.
Copyright
© 1987 - 2000 Rational Software Corporation
|